src/data/playground-configs.ts (1)

8140-8146: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick win

Memos ingress class options lack the empty option now documented in memos.mdx.

The updated memos.mdx documents setting ingress.ingressClassName: "" to omit spec.ingressClassName, mirroring the pattern already used for apache and now olivetin (options: ['', ...]). The memos entry here still only offers ['traefik', 'nginx'], so playground users can't exercise the documented behavior.

♻️ Proposed fix

         {
           label: 'Ingress Class',
           key: 'ingress.ingressClassName',
           type: 'select',
           default: 'traefik',
-          options: ['traefik', 'nginx'],
+          options: ['', 'traefik', 'nginx'],
           description: 'Ingress controller class',
         },

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/data/playground-configs.ts` around lines 8140 - 8146, The Memos ingress
class selector is missing the empty option that is now documented, so update the
playground config entry for ingress.ingressClassName to include an empty choice
alongside the existing traefik and nginx values. Use the existing pattern from
the apache and olivetin config entries in playground-configs.ts, keeping the
same label, key, and description while extending the options list so users can
select "" and omit spec.ingressClassName.

src/data/playground-configs.ts (1)

8424-8451: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Consider exposing DNS/extra-egress controls to match documented behavior.

Per the PR comments, the docs describe networkPolicy.dnsEgress (with its kube-system/k8s-app: kube-dns default selector) and networkPolicy.extraEgress (append custom rules while isolation is enabled) alongside egressIsolation. This section only exposes egressIsolation and the HTTPS CIDR fields, unlike the langflow and kubernetes-mcp-server configs in this same file, which expose analogous dnsEgressPeers[...] and extraEgress[...] fields for their NetworkPolicy sections. If parity with the documentation is desired in the playground, consider adding fields for these two keys.

♻️ Optional fields to add for parity with docs

     {
       name: 'Network Policy',
       collapsible: true,
       gateField: 'networkPolicy.enabled',
       fields: [
         {
           label: 'Egress Isolation',
           key: 'networkPolicy.egressIsolation',
           type: 'toggle',
           default: 'false',
           description: 'Render baseline DNS and HTTPS egress rules',
         },
         {
           label: 'HTTPS IPv4 CIDR',
           key: 'networkPolicy.httpsEgress[0].ipBlock.cidr',
           type: 'text',
           default: '0.0.0.0/0',
           description: 'IPv4 HTTPS egress destination',
         },
         {
           label: 'HTTPS IPv6 CIDR',
           key: 'networkPolicy.httpsEgress[1].ipBlock.cidr',
           type: 'text',
           default: '::/0',
           description: 'IPv6 HTTPS egress destination',
         },
+        {
+          label: 'Extra Egress CIDR',
+          key: 'networkPolicy.extraEgress[0].to[0].ipBlock.cidr',
+          type: 'text',
+          default: '',
+          description: 'Optional additional egress destination',
+        },
       ],
     },

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/data/playground-configs.ts` around lines 8424 - 8451, The Network Policy
playground section exposes only egressIsolation and HTTPS CIDR fields, so it is
missing the documented dnsEgress and extraEgress controls. Update the Network
Policy block in playground-configs by adding fields for networkPolicy.dnsEgress
and networkPolicy.extraEgress, following the same pattern used by the langflow
and kubernetes-mcp-server NetworkPolicy sections. Make sure the DNS field
reflects the kube-system / k8s-app: kube-dns default selector and the
extra-egress field lets users append custom rules while isolation is enabled.